Tom,

I am not sure where that gets configured in the plugin?  This is a screenshot in your manual we have the homing routine specified in the Home area, but I don't see anything about the Var(5) variable?  Is that maybe in Mach3?

Russ

Tom,

I am not sure where that gets configured in the plugin?  This is a screenshot in your manual we have the homing routine specified in the Home area, but I don't see anything about the Var(5) variable?  Is that maybe in Mach3?

Russ

Tom,

We have confirmed we do indeed have a "5" for the variable flag.  We have also turned on the PRINTF function in that MMHome_V7.c program and we can see we are always getting a 7 coming into that home program from Mach3.  This is why it always homes all three axis three times.

The REFALLHOME button in Mach3 script looks like this...

DoButton(24);

DoButton(23);

DoButton(22);

DoButton(25);

DoOEMButton(133);

DoOEMButton(134);

DoOEMButton(135);

Do we need to change something in here?

Russ

Tom,

Actually what we did to get this to pass the flags correctly was to go into the beginning of main in the HomeMM_V7.c program and add the following lines.

int flags persist.data[5];

REQUESTED_HOME_FLAGS = flags;

When we add this to that program at least the machine homes correctly and only once per axis.

Was that home routine written for KmotionCNC primarily?  We found several issues that others probably stumbled on as well.  One for example is that program only supports positive logic homing sensors.  Most optical sensors are active low when the flag enters the sensor.  We had to adjust for that or it always thought it was home and got confused.

On the MPG front that will be more challenging.  The MPG itself moves just fine since it is connected directly to the KFLOP the response is clean and smooth.   Attempting to use it for override will be the challenge.  In MACH3 this works via a Brain, and it works correctly.  In that case the MPG is connected to a second parallel port.  We will run some more experiments by perhaps telling MACH3 that the MPG is connected and perhaps using a Brain again.  I read if you configure Mach with IO it will make the encoder inoperable. 

So close yet so far, each day we get a little closer to getting this completed. 

Russ

7. Within Mach3 - configure IO Bits. 

Various M Codes may be used within Mach3 to activate IO bits on KMotion.  Select the Menu Config|Ports & Pins to bring up the Dialog shown below.  When using the KMotion Plugin, Pin Numbers now correspond to KMotion IO Bit Numbers rather than Parallel port Pins.  Some of the terminology on the screen may be misleading as it was designed expecting to use a parallel port.  For IO bit numbers less than 128 specify Port#1.  For IO bit numbers 128 or larger, subtract 128 from the bit number and specify Port #2 instead of Port #1.  Extended Virtual IO bits 1024-1151 may also be accessed by specifying Port #3 and subtracting 1024 from the bit number (note:  the first 32 Virtual IO will consume less USB bandwidth because they are uploaded in the KFLOP Bulk Status record so use the first 32 if possible). 

Note Mach3 typically defaults after an initial install with Output #1 enabled for spindle control on Pin0 (as shown below).  Bit 0 is often used on a KMotion board as an Encoder input.  Having Mach configure the IO bit as an output will cause the encoder to be inoperable.  Disable the output if this is the case. 

Tom,

Actually what we did to get this to pass the flags correctly was to go into the beginning of main in the HomeMM_V7.c program and add the following lines.

int flags persist.data[5];

REQUESTED_HOME_FLAGS = flags;

When we add this to that program at least the machine homes correctly and only once per axis.

Was that home routine written for KmotionCNC primarily?  We found several issues that others probably stumbled on as well.  One for example is that program only supports positive logic homing sensors.  Most optical sensors are active low when the flag enters the sensor.  We had to adjust for that or it always thought it was home and got confused.

On the MPG front that will be more challenging.  The MPG itself moves just fine since it is connected directly to the KFLOP the response is clean and smooth.   Attempting to use it for override will be the challenge.  In MACH3 this works via a Brain, and it works correctly.  In that case the MPG is connected to a second parallel port.  We will run some more experiments by perhaps telling MACH3 that the MPG is connected and perhaps using a Brain again.  I read if you configure Mach with IO it will make the encoder inoperable. 

So close yet so far, each day we get a little closer to getting this completed. 

Russ

7. Within Mach3 - configure IO Bits. 

Various M Codes may be used within Mach3 to activate IO bits on KMotion.  Select the Menu Config|Ports & Pins to bring up the Dialog shown below.  When using the KMotion Plugin, Pin Numbers now correspond to KMotion IO Bit Numbers rather than Parallel port Pins.  Some of the terminology on the screen may be misleading as it was designed expecting to use a parallel port.  For IO bit numbers less than 128 specify Port#1.  For IO bit numbers 128 or larger, subtract 128 from the bit number and specify Port #2 instead of Port #1.  Extended Virtual IO bits 1024-1151 may also be accessed by specifying Port #3 and subtracting 1024 from the bit number (note:  the first 32 Virtual IO will consume less USB bandwidth because they are uploaded in the KFLOP Bulk Status record so use the first 32 if possible). 

Note Mach3 typically defaults after an initial install with Output #1 enabled for spindle control on Pin0 (as shown below).  Bit 0 is often used on a KMotion board as an Encoder input.  Having Mach configure the IO bit as an output will cause the encoder to be inoperable.  Disable the output if this is the case. 

Tom,

Actually what we did to get this to pass the flags correctly was to go into the beginning of main in the HomeMM_V7.c program and add the following lines.

int flags persist.data[5];

REQUESTED_HOME_FLAGS = flags;

When we add this to that program at least the machine homes correctly and only once per axis.

Was that home routine written for KmotionCNC primarily?  We found several issues that others probably stumbled on as well.  One for example is that program only supports positive logic homing sensors.  Most optical sensors are active low when the flag enters the sensor.  We had to adjust for that or it always thought it was home and got confused.

On the MPG front that will be more challenging.  The MPG itself moves just fine since it is connected directly to the KFLOP the response is clean and smooth.   Attempting to use it for override will be the challenge.  In MACH3 this works via a Brain, and it works correctly.  In that case the MPG is connected to a second parallel port.  We will run some more experiments by perhaps telling MACH3 that the MPG is connected and perhaps using a Brain again.  I read if you configure Mach with IO it will make the encoder inoperable. 

So close yet so far, each day we get a little closer to getting this completed. 

Russ

7. Within Mach3 - configure IO Bits. 

Various M Codes may be used within Mach3 to activate IO bits on KMotion.  Select the Menu Config|Ports & Pins to bring up the Dialog shown below.  When using the KMotion Plugin, Pin Numbers now correspond to KMotion IO Bit Numbers rather than Parallel port Pins.  Some of the terminology on the screen may be misleading as it was designed expecting to use a parallel port.  For IO bit numbers less than 128 specify Port#1.  For IO bit numbers 128 or larger, subtract 128 from the bit number and specify Port #2 instead of Port #1.  Extended Virtual IO bits 1024-1151 may also be accessed by specifying Port #3 and subtracting 1024 from the bit number (note:  the first 32 Virtual IO will consume less USB bandwidth because they are uploaded in the KFLOP Bulk Status record so use the first 32 if possible). 

Note Mach3 typically defaults after an initial install with Output #1 enabled for spindle control on Pin0 (as shown below).  Bit 0 is often used on a KMotion board as an Encoder input.  Having Mach configure the IO bit as an output will cause the encoder to be inoperable.  Disable the output if this is the case.